Secondary user interface

ABSTRACT

An alternate display content controller provides a technique for controlling a video display separately from and in addition to the content displayed on the operating system monitor. Where the display is a computer monitor, the alternate display content controller interacts with the computer utility operating system and hardware drivers to control allocation of display space and create and control one or more parallel graphical user interfaces adjacent the operating system desktop. An alternate display content controller may be incorporated in either hardware or software. As software, an alternate display content controller may be an application running on the computer operating system, or may include an operating system kernel of varying complexity ranging from dependent on the utility operating system for hardware system services to a parallel system independent of the utility operating system and capable of supporting dedicated applications. The alternate display content controller may also include content and operating software delivered over the internet or any other LAN. The alternate display content controller may also be included in a television decoder/settop box to permit two or more parallel graphical user interfaces to be displayed simultaneously.

RELATED APPLICATIONS

This application claims the priority of provisional application serialNo. 60/093,217 filed Jul. 17, 1998 pending.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to user interface displays and, in particular,the use of a parallel user interface separate from the standard userinterface display.

2. Description of the Prior Art

There was a time when the most popular operating system for personalcomputers (DOS) did not include a graphical user interface. Any companycould create a “menu” or “shell” which would be the first programlaunched upon starting the computer and which would present options tothe user for launching and managing various applications. Althoughgraphics programming was difficult in the DOS environment, somecompanies even created graphical user interfaces that could then launchother programs.

Microsoft Corporation of Redmond, Wash., introduced such a graphicaluser interface for launching applications which it called “Windows”. Thefirst three versions of Windows were merely applications which ran underDOS and could be one of numerous items to be selected from a previouslyrunning shell or menu which might be offered by a company other thanMicrosoft. This continued to allow other companies to offer primary userinterface programs to users without the user going through a Microsoftcontrolled user interface.

However, with the introduction by Microsoft of Windows 95™, the initialloading of the operating system presents a Microsoft-developed graphicaluser interface(GUI) at the outset, which occupies the entire screendisplay. This operating system created GUI is commonly known as a“desktop”. As with its previous operating system products, Microsoftarranged with manufacturers of the standard computer hardware to includethis operating system with each computer sold. Microsoft's OEM licensingrestrictions prevent vendors from altering, obscuring, or preceding theMicrosoft desktop display. The Windows environment also presumes itsownership of the entire display and is designed in ways that assume thatit can write to any screen location at any time. With Microsoft'sdomination of this market, it became impossible for other softwarevendors to present an interface to users other than as a Microsoft styleicon within the Microsoft “desktop” consisting of the entire screendisplay. This prompted a need for access to a user interface which couldbe presented outside of the standard computer screen display andtherefore independent of the dictates of Microsoft for items within its“desktop”.

Standard personal computers use VGA or Super VGA or XGA video displaysystems. These display systems operate in standardized graphics modessuch as 640×480 pixels, 800×600 pixels, 1024×768 pixels, and 1280×1024pixels. When one of these display modes is selected, this is the entirearea available for display. In the Microsoft Windows environment, theuser instructs the Windows operating system to select one of thesestandard display modes and the Windows operating system then presentsall of the applications and their icons within the selected displayarea. There is no way at present to cause the Windows “desktop” to useless than the entire display area and still function as intended andallow another program from another vendor to control the remainder. Whatis needed is the ability to designate a portion of video memory aseparate from the Windows desktop, and to make sure that Windowsfunctions normally but at the same time cannot obstruct anythingsubsequently allocated into that space.

SUMMARY OF THE INVENTION

A first aspect of the present invention includes a technique forcontrolling allocation and content of display space among one or moreuser interfaces, operating systems or applications permitting anapplication or parallel graphical user interface (GUI) to operateoutside the desktop, the area designated for display of the operatingsystem interface and it's associated applications. In a first aspect, acomputer operating under the control of any utility operating systemsuch as Microsoft Windows™, Linux, Apple O/S or Unix may have theallocation of visible display controlled by the present invention. Theoperating system desktop may be scaled and/or moved to a specific areaof the display permitting a parallel GUI to operate in the open area.The present invention may be an application operating under the primaryor utility operating system or it may be combined with an operatingsystem kernel to control the display and content in the paralleldisplay.

Another aspect of the present invention includes a technique providedfor adding and using a parallel graphical user interface adjacent to thestandard user graphical display interface, for example in the borderbeyond the standard screen display area. Conventional video systems,such as VGA, SVGA and XGA video systems, include a defined bordersurrounding the display area. The original purpose of this border was toallow adequate time for the horizontal and vertical retrace of theelectron gun in a cathode ray tube display. However, with the advent ofLCD displays and as retrace speeds have increased in modern monitors, itis now possible to present a user interface display in this border. Theborder which can be controlled as a user interface is a portion of whatis known as the “overscan”. This invention is a method for presentingone or more additional or secondary user interfaces, for example, in theoverscan area surrounding the conventional user interface display oftencalled the desktop.

When the electron gun in a CRT retraces to the left of the screen or thetop of the screen, it requires a significant amount of time relative tothe presentation of a scanned line of data. During the retrace, theelectron gun is turned off (“blanked”). If the blanking time requiredfor the retrace is equal to the amount of time available, there is nousable overscan. However, modern monitors have become much faster intheir retrace speeds, leaving a significant amount of time when theelectron gun need not be blanked, allowing a displayable border. In theprior art, although the border is usually “black” (the gun is turnedoff), it is well known how to specify that the border shall be given anyone of six colors. Standard BIOS allows a specification of this color.The desired color is simply specified in one of the registers for thevideo controller. Typically no data for this color is stored in thebuffer of video memory for the display. This invention establishes anadditional video buffer for the border and allows this buffer to bewritten with display data like the regular display buffer. Theadditional video buffer is often present but unused in the graphicssystems of most computers because video memory is usually implemented insizes that are powers of 2e.g. “512K”, whereas standard desktopdimensions are not “e.g. 640×480=300K”. The display area is therebyexpanded, on one or more edges, to provide a visible area previouslyinvisible. The pixels within this newly visible area of the display aremade accessible to programs through an application programming interface(API) component of this invention. A program incorporating a parallelgraphical user interface may be displayed in the previously blanked areaof the display, functionally increasing the accessible area of thedisplay without hardware modification. In other cases the desktop may beincreased or decreased to non-standard sizes.

A further aspect of the present invention includes a method fordisplaying an image on a video display system in an area outside of theprimary display area generated by the video display system. Twodimensions define the standard display area, each specifying a number ofpixels. Selecting a video “mode” specifies these dimensions. The methodis accomplished by adjusting parameters for the video display system toincrease the number of pixels in at least one dimension of the displaysystem. The number of pixels which is added is less than or equal to thedifference between the number of pixels specified in the video mode anda maximum number of pixels which the video display system caneffectively display. Any such difference is defined here as the overscanarea. Thus, the overscan area may be the difference between the currentdesktop video mode and the display capability of the display device ormore specifically, any portion of video memory unused when the operatingsystem is in a given screen dimension. Because all interface displaysare created by writing a desired image to a buffer or memory for thevideo display, the method requires allocating additional video displaymemory for the increased pixels. The image written to such memory isthen displayed by the system alongside the original display area.

In a still further aspect of the present invention, only the verticaldimension is increased and the overscan user interface is presentedabove or below the primary display area. Alternatively, the horizontaldimension may be increased and the overscan user interface displayed tothe right or the left of the primary display area. Similarly, theinterface image may be displayed on any or all of the four sides of theprimary display area.

These and other features and advantages of this invention will becomefurther apparent from the detailed description and accompanying figuresthat follow. In the figures and description, numerals indicate thevarious features of the invention, like numerals referring to likefeatures throughout both the drawings and the description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a standard display of the prior art.

FIG. 2 shows a standard display with an overscan user interface in thebottom overscan area.

FIG. 3 shows a standard display with an overscan user interface on allfour borders of the display.

FIG. 4 shows the components of the computer system that relate to thevideo display system.

FIG. 5 shows a cursor or pointer within the overscan user interface andthe hotspot above it within the standard display.

FIG. 6 shows the usable border within the vertical overscan and thehorizontal overscan surrounding the standard display.

FIG. 7 is an overview flow chart showing the operation of a preferredembodiment of the present invention.

FIG. 8 is a flowchart of the sub-steps in Identify Display step 102 ofFIG. 7.

FIG. 9 is a flowchart of the sub-steps of changing the displayresolution step 114 of FIG. 7.

FIG. 10 is a flowchart of the sub-steps in the Paint the Display step120 of FIG. 7.

FIG. 11 is a flowchart of the sub-steps of Enable Linear Addressing step112 of FIG. 7.

FIG. 12 is a flowchart of the sub-steps of the Process Message Loop ofFIG. 7.

FIG. 13 is a flowchart of the sub-steps of the Check Mouse and KeyboardEvents step 184 in FIG. 12.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

The present invention includes techniques for providing and using anadditional user interface, preferably a secondary graphical userinterface or parallel GUI, to be present on the display at leastapparently simultaneously with the primary user interface, such as theconventional desktop GUI.

In a preferred embodiment, programming mechanisms and interfaces in acomputer system provide the secondary GUI in a convenient and currentlyunused potential display area by providing access and visibility to aportion of the monitor display normally ignored and inaccessible(hereinafter “overscan area”). FIG. 1 shows a standard prior art displaydesktop generated by a Microsoft Windows 95™ operating system. Withinthe desktop 31 are the taskbar 32 and desktop icons 33.

In a preferred embodiment of the present invention, a graphical userinterface image is painted onto one or more of the sides of the overscanarea as shown in FIGS. 2 and 3. FIGS. 2 and 3 show depictions of a SuperVGA (SVGA) display with the addition of a graphical bar user interfacedisplayed in the overscan area. The overscan user interface bar 30 isdefined to reside outside the borders of the “desktop” display area 31.In FIG. 2, the display is modified to include a graphical user interface30 in a bar 20-pixels high below the bottom edge. In FIG. 3, the displayis modified to include a graphical user interface in four bars each20-pixels high/wide outside each of the four display edges: a bottom bar30, a left side bar 34, a right side bar 36, and a top bar 38.

The overscan interface may include, and is not limited to, buttons,menus, application output controls (such as a “ticker window”),animations, and user input controls (such as edit boxes). Because theoverscan interface is not obscured by other applications running withinthe standard desktop, the overscan interface may be constantly visibleor it may toggle between visible and invisible states based upon any ofa number of programming parameters (including, but not limited to, thestate of the active window, the state of a toggle button, etc.).

FIG. 4 is a block diagram of the basic components of the presentinvention. Within the software component S are the operating system 63and one or more applicationssuch as application 61. Within the protectedmodes of modem systems, applications 61 do not have direct access to thevideo or Graphics Drivers 64 or hardware components such as the videocard 66 which contains the video chipset 66A, 66B and 66C. Abstractionlayers such as Application Interface (API) 60, and/or Direct API 62,provide limited access, often through the operating system 63.

The invention provides a technique for painting and accessing an area ofthe computer display not accessible, or used, in the operative desktopgraphics modes. In the Microsoft Windows environments (includingMicrosoft Window 95 and derivatives, and Microsoft Windows NT 4.0 andderivatives) and other contemporary operating environments, the primarydisplay area “desktop” is usually assigned by the operating system to beone of a set of pre-determined video “modes” such as those laid out inTables 1 and 2 below, each of which is predefined at a specific pixelresolution. Thus, the accessible area of the computer display may not bemodified except by selecting another of the available predefined modes.

TABLE 1 ROM BIOS video modes Mode Mode Buffer Seg- Number ResolutionColors Type ment 00H 42 × 25 chars (320 × 350 pixels) 16 Alpha B800 00H42 × 25 chars (320 × 350 pixels) 16 Alpha B800 00H 42 × 25 chars (320 ×400 pixels) 16 Alpha B800 00H 42 × 25 chars (320 × 400 pixels) 16 AlphaB800 01H 42 × 25 chars (320 × 200 pixels) 16 Alpha B800 01H 42 × 25chars (320 × 350 pixels) 16 Alpha B800 01H 42 × 25 chars (320 × 400pixels) 16 Alpha B800 01H 42 × 25 chars (320 × 400 pixels) 16 Alpha B80002H 80 × 25 chars (640 × 200 pixels) 16 Alpha B800 02H 80 × 25 chars(640 × 350 pixels) 16 Alpha B800 02H 80 × 25 chars (640 × 400 pixels) 16Alpha B800 02H 80 × 25 chars (640 × 400 pixels) 16 Alpha B800 03H 80 ×25 chars (640 × 200 pixels) 16 Alpha B800 03H 80 × 25 chars (640 × 350pixels) 16 Alpha B800 03H 80 × 25 chars (640 × 400 pixels) 16 Alpha B80003H 80 × 25 chars (720 × 400 pixels) 16 Alpha B800 04H 320 × 200 pixels4 Graphics B800 05H 320 × 200 pixels 4 Graphics B800 06H 840 × 200pixels 2 Graphics B800 07H 80 × 25 chars (720 × 350 pixels) 2 Alpha B00007H 80 × 25 chars (720 × 400 pixels) 2 Alpha B000 0DH 320 × 200 pixels16 Graphics A000 0EH 640 × 200 pixels 16 Graphics A000 0FH 640 × 350pixels 4 Graphics A000 10H 640 × 350 pixels 4 Graphics A000 10H 640 ×350 pixels 16 Graphics A000 11H 640 × 480 pixels 2 Graphics A000 12H 640× 480 pixels 16 Graphics A000 13H 320 × 200 pixels 256 Graphics A000

TABLE 2 SVGA video modes defined in the VESA BIOS extension Mode NumberResolution Mode Colors Buffer Type 100H 640 × 480 pixels 256 Graphics101H 640 × 480 pixels 256 Graphics 102H 800 × 600 pixels 16 Graphics103H 800 × 600 pixels 256 Graphics 104H 1024 × 768 pixels 16 Graphics105H 1024 × 768 pixels 256 Geaphics 106H 1280 × 1024 pixels 16 Graphics107H 1280 × 1024 pixels 256 Graphics 108H 80 × 60 chars 16 Alpha 109H132 × 25 chars 16 Alpha 10AH 132 × 43 chars 16 Alpha 10BH 132 × 50 chars16 Alpha 10CH 132 × 60 chars 16 Alpha 10DH 320 × 200 pixels 32,768Graphics 10EH 320 × 200 pixels 65,536 Graphics 10FH 320 × 200 pixels16,777,216 Graphics 110H 640 × 480 pixels 32,768 Graphics 111H 640 × 480pixels 65,536 Graphics 112H 640 × 480 pixels 16,777,216 Graphics 113H800 × 600 pixels 32,768 Graphics 114H 800 × 600 pixels 65,536 Graphics115H 800 × 600 pixels 16,777,216 Graphics 116H 1024 × 788 pixels 32,768Graphics 117H 1024 × 768 pixels 65,536 Graphics 118H 1024 × 768 pixels16,777,216 Graphics 119H 1280 × 1024 pixels 32,768 Graphics 11AH 1280 ×1024 pixels 65,536 Graphics 11BH 1280 × 1024 pixels 16,777,216 Graphics

As shown in FIG. 6, a displayed image is “overscanned”. That is, thedisplayed video buffer data occupies less than the entire drivablescreen size. The drivable screen size is determined by the total amountof video memory and the operative video display characteristics. Thewidth of the usable overscan border depends on the amount of thehorizontal overscan 52 reduced by the horizontal blanking 54 and theamount of the vertical overscan 53 reduced by the vertical blanking 55.

In a first preferred embodiment, only a border at the bottom of thestandard display area is used. Consequently, only the vertical controlparameters for the cathode ray tube (CRT) controller, shown as ControlRegisters 6H, 16H, 11H, 10H, 12H and 15H in FIG. 4 need to be adjusted.These parameters and others are shown in Table 3 below:

TABLE 3 Vertical timing parameters for CR programming. Register NameDescription 6H Vertical Total Value = (total number of scan lines perframe) − 2 The high-order bits of this value are stored in the overflowregisters. 7H Overflow High-order bits from other CR registers. 10HVertical Retrace Start scan line at which vertical retrace starts. Thehigh-order bits of this value are stored in the overflow registers. 11HVertical Retrace End Only the low-order 4 bits of the actual VerticalRetrace End value are stored. (Bit 7 is set to 1 to write-protectregisters 0 through 7.) 12H Vertical Display End Scan line at whichdisplay on the screen ends. The high-order bits of this value are storedin the overflow registers. 15H Start Vertical Blank Scan line at whichvertical blanking starts. The high-order bits of this value are storedin the overflow registers. 16H End Vertical Blank Scan line at whichvertical blanking ends. The high order bits of this value are stored inthe overflow registers. 59H-5AH Linear Address Window Position Linearaddress window position in 32-bit CPU address space.

In the standard 640×480 graphics mode, the nominal horizontal scan rateis 31.5 kHz (31,500 times per second) with a vertical scan rate of 60 Hz(60 frames per second). So the number of lines in one frame is31,500/60, or 525. Because only 480 lines of data need to be displayed,there are 525−480, or 45, lines available for vertical overscan. Leavinga more than adequate margin for retrace, which requires only 2 linesworth of time, the preferred embodiment uses 20 lines for the alternatedisplay. Thus the additional 23 unused but available lines may be usedto increase the size of the operating system desktop to somenon-standard size while still allowing two lines for retrace, or may beleft blank, or may be used for one or more additional alternate paralleluser interface displays.

The disclosed method of the preferred embodiment of the presentinvention is accomplished by achieving three requirements:

(1) to address and modify the visible resolution of the video displaysystem such that portions of the overscan area are visible as shown inFIG. 6,

(2) to address and modify the video display contents for the visibleportion of the overscan area, and

(3) to provide an application programming interface (API) or othermechanism to allow applications to implement this functionality.

FIG. 7, and the additional details and sub-steps provided in FIGS. 8-13,provides a flow chart of an implementation of a preferred embodiment ofthe present invention meeting the requirements described above. Theenvironment of this implementation is a standard Microsoft Windows 95™operating environment, using Microsoft Visual C and Microsoft MASM forthe development platform. That is not to imply that this invention islimited in scope to that environment or platform. The invention could beimplemented within any graphical interface environment, such asX-Windows, OSF Motif, Apple OS, a Java OS, and others in which similarvideo standards (VGA, SVGA, XGA, 8514/A) are practiced. The referencebooks PC Video Systems by Richard Wilton, published by Microsoft Pressand Programmer's Guide to the EGA, VGA, and Super VGA Cards by RichardF. Ferrano, published by Addison Wesley provide more than adequatebackground information to implement this embodiment.

Referring now in particular to FIG. 7, upon initialization, at IdentifyDisplay Type step 102, the program attempts to determine the displaytype, and current location in memory used by the display driver, inorder to determine the size and locations of any display modificationsto be made, e.g. to the size and location of overscan area(s) to beused.

As described in further detail in FIG. 8, the program first queries thehardware registry in Query Hardware Registry, step 131, to attempt todetermine the registered display type. If successful, the program thendetermines compatibility information in Display Type Supported, step135, to verify that the program supports that display type and determinememory allocation information.

If the hardware registry information is unavailable, as determined instep 131, or the display type determined in step 131 is unsupported asdetermined by step 104, the program may use an alternate approach, shownas subroutine Query hardware steps 135 in FIG. 8, to query the BIOS, instep 134, and the video chipset 66, in step 136, for similar informationas described immediately below.

If the BIOS is to be accessed in step 134, physical memory is firstallocated in Allocate Physical Memory, step 132, and accessed usingMicrosoft's DPMI (DOS Protected Mode Interface) to map it to the linearmemory address in which the BIOS resides in Use DPMI to assign BIOSlinear address to physical memory, step 133.

Thereafter, the program queries the BIOS in Read BIOS block, Search forVGA/XVA type and manufacturer ID, step 134. If successful, the driverand chipset are then further queried to determine the display type andmemory location in Query driver/chipset for exact chipset, step 136.

If the compatibility information does not indicate a standard VGA, SVGA,XGA, or 8514/A signature, step 134, this routine returns a failure. If aknown chipset manufacturer's identification is found, the driver and/orchipset may be queried with manufacturer-specific routines, step 136, toidentify and initialize, as necessary, the specific chipset.

If, at step 104, the program was unable to finally unable to identifythe display type, either because the registry query in step 131 or thehardware query in step 135 was unsuccessful, the user may be prompted atRun in windowed mode, step 116, as to whether the program shouldcontinue to run as a standard “application bar” or “toolbar”. Theprogram may either exit or proceed to run as a toolbar on the desktop.

Returning now to FIG. 8, if a supported display type is detected, theprogram then determines the screen borders to be accessed in Identifyborders to display in overscan, step 106, based upon user preferences,and determines, as necessary, whether sufficient video memory exists tomake the necessary display changes. For example, if the screen iscurrently set to a 1024×768 resolution at 16 bits-per-pixel, and theprogram is to include four graphical interface bars, one on each edge,with each bar 20 pixels deep, the program must check that video memoryis greater than 1.7 MB (required number of bytes =Pixels Width *BitsPerPixel * PixelsHeight).

The controller registers 6H, 16H, 11H, 10H 12H and 15H as shown in FIG.4 and detailed in Table 3, may be accessed through standard input/outputports, using standard inp/outp functions. The CR registers 6H, 16H, 11H,10H, 12H and 15H must first be unlocked, as indicated in Unlock CRTCregisters, step 108 in FIG. 7, to make them writeable. They are unlockedby clearing bit 7 in controller register 11H.

Addressing of video memory, step 112, is accomplished through one ofseveral means. One is to use the standard VGA 64 Kb “hardware window”,moving it along the video memory buffer 67 (FIG. 4) in 64 Kb incrementsas necessary. The preferred method is to enable linear addressing byquerying the video chipset for the linear window position address, step138 of FIG. 11. This 32-bit offset in memory allows the program to mapthe linear memory to a physical address, steps 140 and 142 of FIG. 11,that can be manipulated programmatically.

At this point the program can modify the size of the display, step 114and FIG. 9, to include the border areas. This routine first checks todetermine whether or not the system is running in “toolbar” mode, step144, and, if so, returns true. If not, it then determines whether toreset all registers and values to their original state, effectivelyreturning the display to its original appearance, step 152. Thedetermination is based upon a number of parameters, such as whether thecurrent resolution, step 146, reflects a standard value or previousprogrammatic manipulation, step 148. If a standard resolution is alreadyset, the variables are reset to include the specified border areas, step150. The CR registers are adjusted, step 154, to modify the scanned andblanked areas of the display. If the top or side areas are modified,existing video memory is moved accordingly in step 162 of FIG. 10.

If any of the foregoing routines returns a failure, the program mayprompt the user to determine whether “emulation” mode, step 13, orwindowed mode step 116 should be used or if the program should exit atstep 124.

In its simplest form, the invention can be treated as a technique foradding a secondary GUI by reconfiguring the actual display mode to add amodified, non-standard GUI mode in which the standard display size orresolution has been adjusted to include a secondary display in additionto the primary display. For example, a standard 640×480 display ismodified in accordance with the present invention to become a largerdisplay, one section of which corresponds to the original 640×480display while another section corresponds to a 640×25 secondary GUIdisplay.

There are various techniques or mechanisms required for modifying thesystem to include the secondary GUI, depending upon the requirements ofthe secondary GUI and upon the present circumstances of the unmodifiedsystem.

In another embodiment of the present invention system resources areallocated for a secondary GUI by fooling the video driver into going tolarger resolution. This technique automatically guarantees that enoughspace is kept clean, since the video driver allocates system resourcesaccording to the resolution that the video driver believes it will beoperating in. To operate one or more secondary user interfaces in one ormore areas of the screen it is necessary to have the memory that wasassociated in video memory or in the frame buffer with that location,contiguously below the primary surface free and available. By writing aseries of small applets specific to hardware known to have systemresource allocation problems for a secondary user interface, thesecondary user interface application may run such applet wheneverresolutions will be switched, initializing the chip set pertinent tothat particular applet. If the application finds an applet pertinent tothe current particular chip set it will be launched. The applet ormini-driver initializes itself, performs the necessary changes to thedriver's video resolution tables, forces a reenable, and sufficientspace is subsequently available for one or more secondary userinterfaces.

When re-enabled, the driver allocates video memory as needed for theprimary display according to the data on the UCCO resolution tables.Therefore, the modified values result in a larger allocation. Once thedriver has allocated memory necessary for the primary surface, thedriver will allow no outside access to the allocated memory. Thus byfooling the driver into believing that it needs to allocate sufficientmemory for a resolution exactly x bytes larger than the currentresolution where x is the size of one or more secondary user interfaces,the application can be sure that no internal or external use of theallocated memory location can conflict with the secondary userinterface.

This method ensures that system resources will be allocated for one ormore secondary user interfaces by writing an applet that would addressthe video driver in such a way as to force the video driver, on its nextreenable, to allocate video memory sufficient for a resolution higherthan the actual operating system resolution. This may also be done bymodifying each instance of the advertised mode tables, and thus creatinga screen size larger than the primary user interface screen size.

This technique has an additional benefit of eliminating the need toprevent the driver from actually shifting into the specified largerresolution, handing the primary user interface a larger display surfaceresolution. The “hardware mode table,” a variant of the aforementionedvideo resolution tables, is not advertised and not accessible.Therefore, when the driver validates the new resolution, checkingagainst the hardware mode table, it will always fail and thereforerefuse to shift into that resolution. Because this technique modifiedthe advertised video resolution tables early enough in the driver'sprocess, allocated memory was modified, and memory addresses set beforethe failure in validate mode. Subsequently when the CRTCs are modified,in step 114, the driver is reserving sufficient memory for one or moresecondary user interfaces and not making it available for any otherprocess or purpose.

In yet another embodiment of the present invention, an enveloping driveris installed to sit above the existing driver and shims itself inbetween the hardware abstraction layer and the actual video driver inorder to be able to handle all calls to the video driver and modify thedriver and the driver's tables in a much more generic fashion ratherthan in a chipset specific fashion. The enveloping driver shims into theprimary video driver, transparently passing calls back and forth to theprimary video driver. The enveloping driver finds the video resolutiontables in the primary video driver which may be in a number of locationswithin the driver. The enveloping driver modifies the tables (forexample, increasing 800 by 600 to 800 by 620). A 1024 by 768 table entrymay become 1024 by 800.

Like the previously described embodiment, the primary driver cannotvalidate the new resolution and therefore cannot actually change thedisplay setting. As a result, the driver allocated memory, allocated thecache space, determined memory address and moved cache and offscreenbuffers as necessary. So the primary driver never uses all the spaceallocated, and will never draw in that space.

As stated earlier, the method of the present invention may include threeprimary steps, finding or producing unused video memory, creating orexpanding the overscan area, and putting data in the overscan area.

The step of finding or producing the unused video memory requires areview of the contents of the Controller Registers, the CR registers,used by VGA compatible chip sets or graphic boards to identify where theoverscan area, the blanking, the vertical and horizontal total and thesinking should be set. The CR defines the desktop display, how itssynched, where its laid out left and right, how much buffer area therewould be on each side, where it would be stored within the video memoryarea. A review of the contents of the CR data registers therefore fullydefines and allows one to control the potential location and size of theoverscan area.

In order to accomplish the step of creating or expanding the overscanarea, the CRs may currently be used directly for systems with videodisplay resolutions up to and including 1024 pixels in any dimension,that is, resolutions which can be defined in the generally accepted VGAstandards by 10 bits per register. To expand the overscan area, new datais written into the CR using standard techniques such as the Inp andOutp, functions. A standard video port and MMIO functions may also beused to modify the CRs.

At greater resolutions, 11 bits may be needed to properly define theresolution. There is currently no standard way in which the 11th bitlocation is defined. Therefore, at a resolution above 1280 by 1024, forexample, an understanding about the video card itself, particularly howthe 11 bits representing the resolution are stored, is currentlyrequired and will be described below in greater detail.

When expanding the overscan, it is important to make sure a previousoverscan bar is not already displayed, possibly from a previous crash orother unexpected problem. Either the display must be immediately resetto the appropriate resolution defaults, or the CR queried to determineif the total screen resolution as understood by the video card anddrivers differs from the screen resolution known by the operating systemdisplay interface. An overscan bar may already be displayed if the totalscreen resolution is not equal to one of the standard VGA or SVGAresolutions. In particular, if the total screen resolution is equal to astandard VGA/SVGA resolution plus the area required for the overscan baror is greater than the resolution reported by the operating systemdisplay interface, the display is reset.

Once the display area or resolution as stored in the CR is determined,the resolution or display area can be extended in several differentways. The overscan area can be added to the bottom, the top, or theright of the current display area, and optionally, the display area canbe repositioned so that the overscan bar can remain centered inappearance. Alternatively. the overscan area can be added anywhere andthe original or desktop display area can be centered to improveappearance. In any event, the height/width of the display area requiredfor the overscan bar is presented adjacent the desktop area stored inthe CR and the combination is written into the CR, overwriting theprevious data.

The screen typically shows a quick flash as it is placed in a differentmode, including the desktop display area as well as a parallel GUI suchas a display bar in the overscan area. As soon as that change occurs, ablack mask can be positioned over the new areas. The new menu data canthen be safely written on top of the black mask so that the user neversees memory “garbage”.

There is typically a few seconds of load time during which a simplemessage can be displayed, such as “Loading . . . ”, to avoid confusingthe user.

There are a number of mechanisms by which this may be done. A set ofclass objects is used, all derived from a common base classcorresponding to the above described VGA-generic technique.

The first mechanism is an implementation of the VGA-generic technique.Using this mechanism, no information specific to a video-card isnecessary, other than ensuring VGA support. Using standard applicationprogramming interface (API) routines, primary and secondary surfaces areallocated. The new display data in the CR is simply the physical addressat the start of the primary surface plus the number of pixels defined bythe screen size.

Allocation of the primary surface will always be based on the entirescreen display. Given the linear address of the allocated primarysurface, from which a physical address can be derived, it can beextrapolated that the physical address of the location in video memoryimmediately adjacent to the primary surface is represented by the sum ofthe number of bytes of memory used to maintain the primary surface inmemory plus the value of the physical address of the primary surface.

Once the physical address of the primary surface is known, the size ofthe primary surface as represented in video memory can be determined.

For example, the system looks in the CRs for the resolution of thescreen, 800 by 600, in terms of number of bits per pixel, or bytes perpixel. Then any data stored in the CR representing any horizontalsynching space is added. This is the true scan line length. The scanline length is a more accurate measurement of the width in a givenresolution.

Next, the physical address of the allocated secondary surface is derivedfrom its linear address. In the case where the allocated secondarysurface is, in fact, allocated in the memory space contiguous to theprimary surface (the value of the secondary surface physical address isequal to the value of the primary surface physical address plus the sizeof the primary), the secondary surface is determined to be the locationin memory for the overscan display.

If, however, the above is not true and the secondary surface is notcontiguous to the primary surface, another approach mechanism isrequired.

To summarize, the first mechanism determines how much physical area toallocate for the desktop allowing adjacent area for parallel GUIsecondary space beyond that to display in the overscan area. The newlyallocated area will be the very first block of memory available. If thisblock immediately follows the primary surface, the physical address willcorrespond to the value associated with the physical address of theprimary surface, plus the size of the primary surface. If that is true,the memory blocks are contiguous, this VGA-generic mechanism can beused.

If this first, VGA-generic mechanism cannot be used, the video card anddriver name and version information retrieved from the hardware registryand BIOS, as described earlier, is used in conjunction with a look-uptable to determine the best alternatives among the remaining mechanisms.The table includes a set of standards keyed to the list of driver namesfound in the hardware registry. A class object specific to the videochipset is instantiated based, directly or indirectly, on theVGA-generic object.

If the hardware look up does not result in a reliable match, areliability, or confidence, fudge factor may be used. For example, ifthe hardware look up determines that an XYZ-brand device of some kind isbeing used, but the particular XYZ device named is not found in the lookup table, a generic model from that chipset manufacturer many often beusable. If no information is available, the user may get a messageindicating that the hardware is not supported and that the programcannot run in the overscan area. The user may then be queried todetermine if the system should be operated in the “application-toolbar”mode, which basically runs with exactly the same functionality but in awindowed environment within the desktop rather than in the overscan areaoutside the desktop.

The next alternative mechanism uses surface overlays. The first step tothis approach is to determine if the system will support surfaceoverlays. A call is made to the video driver to determine what featuresare supported and what other factors are required. If surface overlaysare supported, for example, there may be a scaling factor required.

For example, a particular video card in a given machine, using 2megabytes of video RAM might support unscaled surface overlays at1024×768 at 8 bits per pixel, but not at 1024×768 at 16 bits per pixelbecause the bandwidth of the video card or the speed of the card,coupled with the relatively small amount of video memory would not besufficient to draw a full width overlay. It is often horizontal scalingthat is at issue, preventing the driver from drawing a full widthoverlay. An overlay is literally an image that is drawn on top of theprimary surface. It is not a secondary surface, which is describedabove. Typically, the system sends its signal from the video driver tothe hardware such that it merges the two signals together, overlaying asecond signal on top of the first.

If a system can not support unscaled overlays, perhaps because ofbandwidth issues or memory issues, this mechanism is not desirable. Itis not rejected, but becomes a lower priority alternative. For example,if the scaling factor is below 0.1, then the normal bar can be drawn andit will be clipped closer to the edge. If the scaling factor is morethan 10%, another approach mechanism is required.

In the next set of alternative mechanisms, a secondary surface isallocated sufficient in size to encompass the normal desktop displayarea plus the overscan area to be used for display of the overscan baror bars. Using these mechanisms, the allocated secondary surface doesnot have to be located contiguous in memory to the primary surface.However, these approaches use more video memory than the others.

The first step is to allocate a secondary surface sufficient in size tocontain the video display (the primary surface) plus the overscan areato be used. If the allocation fails, that means that there is not enoughvideo memory to accomplish the task and this set of mechanisms isskipped and the next alternative tried. After the new block of memory isallocated, a timer of very small granularity is used to execute a simplememory copy of in the contents of the primary surface onto theappropriate location of this secondary surface. The timer executes thecopy at approximately 85 times per second.

Within this set of alternative mechanisms is a variant that uses thesystem page tables. This mechanism queries the system page tables todetermine the current GDI surface address, that is, the physical addressin the page table for the primary surface. A secondary surface is thencreated large enough to hold all of what is in the video memory plus thememory required for the overscan bar to be displayed. This surfaceaddress is then pushed into the system page table and asserted as theGDI surface address.

Thereafter, when GDI reads from or writes to the primary surface throughthe driver, it actually reads from or writes the new, larger surface.The overscan bar program can, subsequently, modify the area of thesurface not addressed by GDI. The original primary surface can bede-allocated and the memory usage reclaimed. This mechanism, being morememory-efficient than the previously described mechanism, is thepreferred alternative. But the page tables solution will not workcorrectly on a chipset that includes a coprocessor device. If theinitial device query reveals that the device does include a coprocessor,this variant mechanism will not be attempted.

Other variations of the above-described mechanisms are accounted for inderived class objects. For example, the VGA-generic mechanisms may varywhen the video card requires more than ten bits to represent the videoresolution in the CR. Some instances may require 11 bits. Such registerstypically do not use contiguous bytes, but use extension bits todesignate the address information for the higher order bits.

In this example, the eleventh bit is usually specified in an extended CRregister and the extended CR registers are usually chip specific.

Similarly, a variation of the surface overlay mechanism includes ascaling factor, as described above. This alternative is handled inspecific implementations through derived class objects and may be thebest solution in certain situations.

Phase 2 of the invention begins by painting the new images into astandard off-screen buffer, step 118, as is commonly used in the art,and making the contents visible, step 120, as described in FIG. 10. Ifthe program is in “toolbar” mode, step 156, the off-screen buffer ispainted into the standard window client space, step 166, and madevisible, step 164, using generic windowing-system routines. Otherwise,the linear window position address is mapped, step 158, as described inFIG. 11 which has been previously explained. Once the linear memory ismapped to a physical memory address, step 142, the contents of theoff-screen display buffer can be copied into the video buffer directly,step 154 of FIG. 10, or painted as to a secondary surface.

The preferred embodiment application includes a standard applicationmessage loop, step 122, which processes system and user events. Anexample of a minimum functionality process loop is in FIG. 12. Here theapplication handles a minimal set of system events, such as paintingrequests, step 170, system resolution changes, step 172, andactivation/deactivation, step 174. Here, too, is where user events, suchas key or mouse events, may be handled, step 184, detailed in FIG. 13.System paint messages are handled by painting as appropriate into theoff-screen buffer, step 178, and painting the window or display buffer,step 180, as appropriate, as described earlier in FIG. 10. Systemresolution messages are received whenever the system or user changes thescreen or color resolution. The programs reset all registers to thecorrect new values, then change the display resolution, step 182, asearlier described in FIG. 9, to reflect the new resolution modified.User messages are ignored when the program is not the activeapplication.

FIG. 13 describes a method of implementing user-input events. In thisembodiment, there are three alternative mechanisms used to implementcursor or mouse support so that the user has a pointing device inputtool within the overscan area user interface.

In the preferred mechanism, GDI's “cliprect” is modified to encompassthe overscan bar's display area. That keeps the operating system fromclipping the cursor as it moves into the overscan area. This changedoesn't necessarily make the cursor visible or provide event feedback tothe application, but is the first step.

Some current Windows applications continually reset the cliprect. It isa standard programming procedure to reset the cliprect after use or lossof input focus. Some applications use the cliprect to constrain themouse to a specific area as may be required by the active application.Whenever the overscan display bar interface receives the input focus itreasserts the cliprect, making it large enough for the mouse to traveldown into the overscan space.

Once the cliprect has been expanded, the mouse can generate messages tothe operating system reflecting motion within the expansion area. GDIdoes not draw the cursor outside what it understands to be itsresolution, however, and does-not pass “out-of-bounds” event messages onto an application. The overscan program uses a V×D device driver, andrelated callback function, to make hardware driver calls at privilege orprotection ring zero to monitor the actual physical deltas, or changes,in the mouse position and state. Every mouse position or state change isreturned as an event to the program which can graphically represent theposition within the menu display bar.

An alternative mechanism avoids the need to expand the cliprect in orderto avoid conflict with a class of device drivers that use the cliprectto facilitate virtual display panning. Querying the mouse input devicedirectly the overscan program can determine “delta's”, changes inposition and state. Whenever the cursor touches the very last row orcolumn of pixels on the standard display, it is constrained there bysetting the cliprect to a rectangle comprised of only that last row orcolumn. A “virtual” cursor position is derived from the deltas availablefrom the input device. The actual cursor is hidden and a virtual cursorrepresentation is explicitly displayed at the virtual coordinates toprovide accurate feedback to the user. If the virtual coordinates moveback onto the desktop from the overscan area, the cliprect is cleared,the virtual representation removed, and the actual cursor restored ontothe screen.

A third alternative mechanism creates a transparent window that overlapsthe actual Windows desktop display area by a predefined number ofpixels, for example, two or four pixels. If the mouse enters that small,transparent area, the program hides the cursor. A cursor image is thendisplayed within the overscan bar area, at the same X-coordinate but ata Y-coordinate correspondingly offset into the overscan area. If atwo-pixel overlap area is used, this method uses a granularity of two.Accordingly, this API-only approach provides only limited verticalgranularity. This alternative mechanism assures that all implementationswill have some degree of mouse-input support, even when cliprect andinput device driver solutions fail.

FIG. 7 describes the cleanup mechanisms executed when the program isclosed, step 124. The display is reset to the original resolution, step126, and the CR registers are reset to their original values, step 128,and locked, step 130.

In another embodiment of the present invention, the launching orinitiating of alternate display content controller 6 may be modified andcontrolled. Alternate display content controller 6 may be launched as aservice, as an application, or as a user application. As a service,alternate display content controller 6 may be launched as a servicewithin the registry of utility operating system 5B. The first kind ofapplication is launched in the Run section in the registry, and the userapplication may be initiated from the Start Up Group within the Startbutton. Thus, alternate display content controller 6 may be initiatedany time from the first thing after graphics mode is enabled to the verylast thing initiated.

Launched as a service, alternate display content controller 6 may bevisible shortly after utility operating system 5B such as Windowsactually addresses the display, and how soon after depends on wherealternate display content controller 6 is put it in the order of thethings that will be launched as services. It may be possible to putalternate display content controller 6 so that it launches asessentially the first service and thus would launch almost at the sametime as the drivers, very, very shortly after the drivers are launched.Accordingly, it is possible to have the screen change from text mode tographics, draw the colored background, immediately re-display with theoverscan addressed and a parallel GUI such as CSNB 2 display the veryclose to the same time as taskbar. Launched as a run-line application,alternate display content controller 6 may be visible in display space 1shortly after icons appear.

Alternative Embodiments

1. Utilizing the VESA BIOS Extensions (VBE) in place of the CRTController registers (FIG. 5) to determine the linear window positionaddress, step 138, as necessary.

2. Utilizing API's (application programming interfaces) 62 capable ofdirect driver and/or hardware manipulation, such as Microsoft's DirectXand/or DirectDraw, in place of the CRT Controller registers and/ordirect access to the display buffer.

3. Utilizing API's (applications programming interfaces) 62, such asMicrosoft's DirectX and/or DirectDraw, capable of direct driver and/orhardware manipulation, to create a second virtual display surface on theprimary display with the same purpose, to display a separate andunobscured graphical user interface.

4. Utilizing modifications in the video subsystem of the operatingsystem 63 in place of the CRT Controller registers and/or DirectX accessto the display buffer.

5. Utilizing modifications in the video subsystem of the operatingsystem 63 to create a second virtual display surface on the primarydisplay with the same purpose, to display a separate and unobscuredgraphical user interface.

6. Building this functionality into the actual video drivers 64 and/ormini-drivers. Microsoft Windows provides support for virtual devicedrivers, V×Ds, which could also directly interface with the hardware anddrivers. These could also include an API to provide applications with aninterface to the modified display.

7. Incorporating the same functionality, with or without the VGAregisters, into the BIOS and providing an API to allow applications aninterface to the modified display.

8. Incorporating the same functionality into hardware devices, such asmonitor itself, with hardware and/or software interfaces to the CPU.

9. This technique may be used to control the desktop (i.e. Windows) toeasily enable the desktop to operate in virtually any non-standard sizelimited only by the capability of the display hardware. This may be incombination with parallel graphical user interface displays orexclusively to maximize the primary operating system desktop displayarea. This may not require any modification to the operating system.

In overview, the visual display area is conventionally defined by thevalues maintained in the CRTC registers on the chip and available to thedriver. The normally displayed area is defined by VGA standards, andsubsequently by SVGA standards, to be a preset number of modes, eachmode including a particular display resolution which specifies the areaof the display in which the desktop can be displayed.

The desktop can only be displayed in this area because Windows does notdirectly read/write the video memory, rather it uses programminginterface calls to the video driver. And the video driver simplyreads/writes using an address that happens to be in video memory. So thevalue this mechanism needs to realize is the value the video card anddriver assert is available for painting. This value is queried from theregisters, modified by specific amounts and rewritten to the card.Subsequently, the present invention changes the area of writeablevisible display space without informing the operating system's displayinterface of the change

This invention doesn't necessary change the CRTCs to add just to thebottom. Preferably the top is also moved up a little. This keeps thedisplayed interfaces centered within the drivable display area. Forexample, rather than just add thirty-two scan lines to the bottom, thetop of the display area is moved up by sixteen lines.

Nor does this invention depend solely upon the ability to change theCRTCs to modify the visible display area. Alternative mechanisms defineother methods of creating and accessing visible areas of the screen thatare outside the dimensions of the desktop accessed by the operatingsystem's display interface.

From a consideration of the specifications, drawings, and claims, otherembodiments and variations of the invention will be apparent to oneskilled in the art of computer science.

In particular, the secondary GUI may be positioned in areas not normallyconsidered the conventional overscan area. For example, the secondaryGUI may be positioned in a small square exactly in the center of thenormal display in order to provide a service required by the particularsystem and application. In fact, the techniques of reading and rewritingscreen display information can be used within the scope of the inventionto maintain the primary GUI information, or portions of it, in anadditional memory and selectively on a timed, computed, interactive, orany or other basis, replace a portion of the primary GUI with thesecondary GUI such as a pop-up, window, or any other display space.

As a simple example, a security system may require the ability todisplay information to a user without regard to the status of thecomputer system and/or require the user to make a selection, such ascall for help by clicking on “911?”. The present invention could providea video display buffer in which a portion of the primary GUI interfacewas continuously recorded and displayed in a secondary GUI for examplein the center of the screen. Under non-emergency conditions, thesecondary GUI would then be effectively invisible in that the User wouldnot notice anything except the primary GUI.

Under the appropriate emergency conditions, an alarm monitor could causethe secondary GUI to present the “911?” to the user by overwriting thecopy of the primary display stored in the secondary GUI memory.Alternatively, a database of photographs may be stored and one recalledin response to an incoming phone call in which caller ID identified aphone number associated with a database photo entry.

In general, the present invention may provide one or more secondary userinterfaces which may be useful whenever it is more convenient ordesirable to control a portion of the total display, either outside theprimary display in an unused area such as overscan or even in a portionof the primary GUI directly or by time division multiplexing, directlyby communication with the video memory, or by bypassing at least aportion of the video memory to create a new video memory. In otherwords, the present invention may provide one or more secondary userinterfaces outside of the control of the system, such as the operatingsystem, which controls the primary GUI.

Additional user interfaces may be used for a variety of differentpurposes. For example, a secondary user interface may be used to providesimultaneous access to the Internet, full motion video, and a conferencechannel. A secondary user interface may be dedicated to a local networkor multiple secondary user interfaces may provide simultaneous accessand data for one or more networks to which a particular computer may beconnected.

The software code or computer instructions that implement the techniquesof the present invention are included in Appendix A.

Having now described the invention in accordance with the requirementsof the patent statutes, those skilled in this art will understand how tomake changes and modifications in the present invention to meet theirspecific requirements or conditions. Such changes and modifications maybe made without departing from the scope and spirit of the invention asset forth in the following claims.

We claim:
 1. A method for enabling the display of an image on a videodisplay system in an area outside of a display area controlled by acomputer operating system, the computer operating system presenting auser interface that occupies at least a portion of the display area, thevideo display system having a total displayable area of which thedisplay area controlled by the computer operating system is a part,comprising: modifying the total displayable area of the video displaysystem to include a second display area by adjusting the parameters ofthe video display system; when the modified displayable area is largerthan before modification, locating additional video display memory tocorrespond to the second display area, thereby creating an increasedamount of video display memory that is addressable; allocating themodified displayable area between the display area that is controlled byoperating system user interface and the second display area; writing theimage to the video display memory that corresponds to the second displayarea in accordance with the allocation of the modified displayable area;and transferring the video display memory contents to the video displaysystem so that the image is displayed in conjunction with the operatingsystem user interface and outside of the control of the operating systemuser interface.
 2. The method of claim 1 wherein the allocating of themodified displayable area decreases the size of the portion of thedisplayable area that is controlled by the operating system userinterface relative to the size of the total displayable area.
 3. Themethod of claim 2 wherein the modified displayable area is larger thanbefore modification.
 4. The method of claim 1 wherein the modifieddisplayable area is larger than before modification and the allocatingof the modified displayable area increases the size of the display areathat is controlled by the operating system user interface.
 5. The methodof claim 4 wherein the increased size of the display area allocated tothe operating system user interface is not a standard video resolutionmode size.
 6. The method of claim 1 wherein the modifying of displayablearea further comprises adjusting the parameters of the video displaysystem to increase the number of displayable pixels in at least onedimension of the displayable area to less than or equal to the maximumnumber of pixels that can be effectively displayed by the video displaysystem.
 7. The method of claim 6 wherein the adjusting the parameters ofthe video display system is performed using techniques that addresspixels in an overscan area of the video display system.
 8. The method ofclaim 7 wherein the image is displayed in at least a portion of pixelsin the overscan area and includes a movable pointer that moves inrelation to user input.
 9. The method of claim 8 wherein the pointer hasan associated tip that is positioned outside of a cursor activationpoint associated with the tip, the cursor activation point remainingwithin the display area controlled by the operating system userinterface while the pointer is displayed within the image.
 10. Themethod of claim 6 wherein the adjusted parameters are control parametersfor a controller of a cathode ray tube display.
 11. The method of claim1 wherein the modified displayable area is enlarged to include a seconddisplay area by increasing the number of displayable pixels in at leastone dimension of the displayable area.
 12. The method of claim 11wherein the dimension in which the number of displayable pixels isincreased is vertical and the image is displayed below the operatingsystem user interface.
 13. The method of claim 11 wherein the dimensionin which the number of displayable pixels is increased is vertical andthe image is displayed above the operating system user interface. 14.The method of claim 11 wherein the dimension in which the number ofdisplayable pixels is increased is horizontal and the image is displayedto the left of the operating system user interface.
 15. The method ofclaim 11 wherein the dimension in which the number of displayable pixelsis increased is horizontal and the image is displayed to the right ofthe operating system user interface.
 16. The method of claim 11 whereinthe dimension in which the number of displayable pixels is increased isboth horizontal and vertical and the image is displayed on a verticalside of the operating system user interface and on a horizontal side ofthe operating system user interface.
 17. The method of claim 1 whereinthe modifying of the total displayable area of the video display systemto include the second display area by adjusting the parameters increasesthe displayable area to a standard resolution supported by the videodisplay system.
 18. The method of claim 1 wherein the adjusting of theparameters and the allocating of the modified displayable area furthercomprises: intercepting a request from the operating system to use afirst higher video resolution mode; requesting the video display systemto use a second higher video resolution mode that is higher than thefirst higher video resolution mode; allocating to the display areacontrolled by the operating system user interface the portion of thedisplayable area that corresponds to the first higher video resolutionmode; and allocating to the second display area for displaying the imagethe increased displayable area between the first higher video resolutionmode and the second higher video resolution mode.
 19. The method ofclaim 1 wherein the adjusting of the parameters and the allocating ofthe modified displayable area further comprises: intercepting a requestfrom the operating system to use a higher video resolution mode that ishigher than a current resolution mode; allocating to the display areacontrolled by the operating system user interface the displayable areathat corresponds to the current resolution mode; and allocating to thesecond display area for displaying the image the increased displayablearea between the higher video resolution mode and the current videoresolution mode.
 20. The method of claim 1 wherein the adjusting of theparameters and the allocating of the modified displayable area furthercomprises: intercepting a request from the operating system to use afirst higher video resolution mode; requesting the video display systemto use the first higher video resolution mode, thereby resulting in anincreased total displayable area; allocating to the display areacontrolled by the operating system user interface a portion of theincreased displayable area; and allocating to the second display areafor displaying the image the remaining portion of the increaseddisplayable area.
 21. The method of claim 1 wherein at least a portionof the image is displayed along with the operating system user interfacein a manner that prohibits the operating system user interface fromoverwriting the portion of the image.
 22. A display controller forenabling the display of a secondary user interface on a video displaysystem in conjunction with a primary user interface presented by aseparately controlled program on a display area of the video displaysystem, comprising: display adjustment facility that modifies the totaldisplayable area of the video display system to include a second displayarea by adjusting the parameters of the video display system; memorylocator that locates additional video display memory to correspond tothe second display area when the modified total displayable area isenlarged, thereby creating an increased amount of video display memorythat is addressable; display allocation facility that allocates themodified displayable area between the primary user interface and thesecondary user interface; and display transfer mechanism that writes thesecondary user interface to the video display memory that corresponds tothe second display area in accordance with the allocation of themodified displayable area and transfers the video display memorycontents to the video display system so that the secondary userinterface is displayed in conjunction with the primary user interface.23. The system of claim 22 wherein the display allocation facilitydecreases the size of the portion of the displayable area that iscontrolled by the primary user interface relative to the size of thetotal displayable area.
 24. The system of claim 23 wherein the displayadjustment facility enlarges the total displayable area.
 25. The systemof claim 22 wherein the display adjustment facility enlarges the totaldisplayable area and the display allocation facility increases the sizeof the display area that is controlled by the primary user interface.26. The system of claim 25 wherein the increased size of the displayarea allocated to the primary user interface is not a standard videoresolution mode size.
 27. The system of claim 22 wherein the displayadjustment facility modifies the displayable area by adjusting theparameters of the video display system to increase the number ofdisplayable pixels in at least one dimension of the displayable area toless than or equal to the maximum number of pixels that can beeffectively displayed by the video display system.
 28. The system ofclaim 27 wherein the display adjustment facility adjusts the parametersof the video display system using techniques that address pixels in anoverscan area of the video display system.
 29. The system of claim 28wherein the display transfer mechanism displays the secondary userinterface in at least a portion of pixels in the overscan area with amovable pointer that moves in relation to user input.
 30. The system ofclaim 29 wherein the movable pointer has an associated tip that ispositioned outside of a cursor activation point associated with the tip,the cursor activation point remaining within the display area controlledby the primary user interface while the pointer is displayed within thesecondary user interface.
 31. The system of claim 27 wherein theparameters adjusted by display adjustment facility are controlparameters for a controller of a cathode ray tube display.
 32. Thesystem of claim 22 wherein the display adjustment facility enlarges thetotal displayable area to include a second display area by increasingthe number of displayable pixels in at least one dimension of thedisplayable area.
 33. The system of claim 32 wherein the dimension inwhich the number of displayable pixels is increased is vertical and thesecondary user interface is displayed below the primary user interface.34. The system of claim 32 wherein the dimension in which the number ofdisplayable pixels is increased is vertical and the secondary userinterface is displayed above the primary user interface.
 35. The systemof claim 32 wherein the dimension in which the number of displayablepixels is increased is horizontal and the secondary user interface isdisplayed to the left of the primary user interface.
 36. The system ofclaim 32 wherein the dimension in which the number of displayable pixelsis increased is horizontal and the secondary user interface is displayedto the right of the primary user interface.
 37. The system of claim 32wherein the dimension in which the number of displayable pixels isincreased is both horizontal and vertical and the secondary userinterface is displayed on a vertical side of the primary user interfaceand on a horizontal side of the primary user interface.
 38. The systemof claim 22 wherein the display adjustment facility modifies the totaldisplayable area to include the second display area by adjusting theparameters to increase the displayable area to a standard resolutionsupported by the video display system.
 39. The system of claim 22wherein the display adjustment facility and display allocation facilityfurther comprise hooking mechanism that intercepts a request from theseparately controlled program to use a first higher video resolutionmode; requests the video display system to use a second higher videoresolution mode that is higher than the first higher video resolutionmode; allocates to the display area controlled by the primary userinterface the portion of the displayable area that corresponds to thefirst higher video resolution mode; and allocates to the second displayarea controlled by the secondary user interface the increaseddisplayable area between the first higher video resolution mode and thesecond higher video resolution mode.
 40. The system of claim 22 whereinthe display adjustment facility and display allocation facility furthercomprise hooking mechanism that intercepts a request from the separatelycontrolled program to use a higher video resolution mode that is higherthan a current resolution mode; allocates to the display area controlledby the primary user interface the displayable area that corresponds tothe current resolution mode; and allocates to the second display areacontrolled by the secondary user interface the increased displayablearea between the higher video resolution mode and the current videoresolution mode.
 41. The system of claim 22 wherein the displayadjustment facility and display allocation facility further comprisehooking mechanism that intercepts a request from the separatelycontrolled program to use a first higher video resolution mode; requeststhe video display system to use the first higher video resolution mode,thereby increasing the total displayable area; allocates to the displayarea controlled by the primary user interface a portion of the increaseddisplayable area; and allocates to the second display area controlled bythe secondary user interface the remaining portion of the increaseddisplayable area.
 42. The system of claim 22 wherein the displaytransfer mechanism displays at least a portion of the secondary userinterface along with the primary user interface in a manner thatprohibits the primary user interface from overwriting the portion of thesecondary user interface.
 43. The system of claim 22, wherein thedisplay adjustment facility adjusts the parameters of the video displaysystem by performing function calls to driver software of the videodisplay system.
 44. A computer readable memory medium containinginstructions for controlling a computer processor to display a secondaryuser interface on a video display system in conjunction with the displayof, on a display area of the video display system, a primary userinterface of a separately controlled program, by: modifying the totaldisplayable area of the video display system to include a second displayarea by adjusting the parameters of the video display system; when themodified displayable area is larger than before modification, locatingadditional video display memory to correspond to the second displayarea, thereby creating an increased amount of video display memory thatis addressable; allocating the modified displayable area between theprimary user interface and the secondary user interface; writing thesecondary user interface to the video display memory that corresponds tothe second display area in accordance with the allocation of themodified displayable area; and transferring the video display memorycontents to the video display system so that the secondary userinterface is displayed in conjunction with the primary user interfaceand outside of the control of the primary user interface.
 45. A computerreadable memory medium of claim 44 wherein the allocating of themodified displayable area decreases the size of the portion of thedisplayable area that is controlled by the primary user interfacerelative to the size of the total displayable area.
 46. A computerreadable memory medium of claim 45 wherein the modified displayable areais enlarged.
 47. A computer readable memory medium of claim 44 whereinthe modified displayable area is larger than before modification and theallocating of the modified displayable area increases the size of thedisplay area that is controlled by the primary user interface.
 48. Acomputer readable memory medium of claim 47 wherein the increased sizeof the display area allocated to the primary user interface is not astandard video resolution mode size.
 49. A computer readable memorymedium of claim 44 wherein the modifying of displayable area furthercomprises adjusting the parameters of the video display system toincrease the number of displayable pixels in at least one dimension ofthe displayable area to less than or equal to the maximum number ofpixels that can be effectively displayed by the video display system.50. A computer readable memory medium of claim 49 wherein the adjustingthe parameters of the video display system is performed using techniquesthat address pixels in an overscan area of the video display system. 51.A computer readable memory medium of claim 44 wherein the secondary userinterface is displayed in at least a portion of pixels in the overscanarea and includes a movable pointer that moves in relation to userinput.
 52. A computer readable memory medium of claim 51 wherein thepointer has an associated tip that is positioned outside of a cursoractivation point associated with the tip, the cursor activation pointremaining within the display area controlled by the primary userinterface while the pointer is displayed within the secondary userinterface.
 53. A computer readable memory medium of claim 44 wherein themodifying of the total displayable area of the video display system toinclude the second display area by adjusting the parameters increasesthe displayable area to a standard resolution supported by the videodisplay system.
 54. A computer readable memory medium of claim 44wherein the adjusting of the parameters and the allocating of themodified displayable area is performed by: intercepting a request fromthe primary user interface; requesting the video display system to usedifferent video resolution mode, thereby modifying the size of thedisplayable area; and allocating the modified display area between theprimary user interface and the secondary user interface.
 55. A computerreadable memory medium of claim 44 wherein at least a portion of thesecondary user interface is displayed along with the primary userinterface in a manner that prohibits the primary user interface fromoverwriting the portion of the secondary user interface.